-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Expanding Swift Self to class members and value types #248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Referencing Objective-C key-paths
Proposal: SwiftPM System Module Search Paths
Final writeup of the property selector proposal
Update README to move SE-0046 to implemented
…e wrong thread with the wrong title and subsequently corrected.
When the core team makes a decision regarding a proposal, we will start adding it to the proposal here.
|
Updated per Joe Groff's @jckarter suggestions on-list: "It's been pitched before, but I don't think we've had a dedicated thread to this idea. Erica has proposed making |
|
@jckarter You know what? I seem to have mucked up the pull request process again. Going to try with a clean branch. Watch the pull space. Closing this. |
Within a class scope,
Selfmeans "the dynamic class ofself". This proposal extends that courtesy to value types, where dynamicSelfwill match a construct's static type, and to the bodies of class members, where it may not. It also introduces a static variation,#Selfthat expands to static type of the code it appears within.This proposal was discussed on the Swift Evolution list in the [Pitch] Adding a Self type name shortcut for static member access thread.